Skip to content

Avoid non-standard approaches for warning emitting #242

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 9, 2022

Conversation

asvetlov
Copy link
Contributor

@asvetlov asvetlov commented Jan 9, 2022

No description provided.

@codecov-commenter
Copy link

codecov-commenter commented Jan 9, 2022

Codecov Report

Merging #242 (8864cb7) into master (f86d900) will decrease coverage by 0.16%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #242      +/-   ##
==========================================
- Coverage   95.59%   95.43%   -0.17%     
==========================================
  Files           2        2              
  Lines         227      219       -8     
==========================================
- Hits          217      209       -8     
  Misses         10       10              
Impacted Files Coverage Δ
pytest_asyncio/plugin.py 95.37% <100.00%> (-0.17%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f86d900...8864cb7. Read the comment docs.

@asvetlov asvetlov requested review from seifertm and Tinche January 9, 2022 06:51
@asvetlov asvetlov changed the title Avoid non-standard approached for warning emitting Avoid non-standard approaches for warning emitting Jan 9, 2022
@asvetlov asvetlov merged commit 0a143c4 into master Jan 9, 2022
@asvetlov asvetlov deleted the standard-issue-config-emitter branch January 9, 2022 13:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants